CVE-2026-2974
AliasVault App Backup aliasvault.xml backup
Description
A vulnerability was identified in AliasVault App up to 0.25.3 on Android/iOS. This vulnerability affects unknown code of the file shared_prefs/aliasvault.xml of the component Backup Handler. The manipulation of the argument accessToken/refreshToken/metadata/key_derivation_params/auth_methods leads to exposure of backup file to an unauthorized control sphere. An attack has to be approached locally. The attack is considered to have high complexity. It is stated that the exploitability is difficult. The exploit is publicly available and might be used. Upgrading to version 0.26.0 is able to resolve this issue. The identifier of the patch is 873ecc03f92238e162f98a068ad56069a922b4f6/0bd662320174d8265dfe3b05a04bc13efc960532. It is recommended to upgrade the affected component. The creator of the software explains: "Because of AliasVault's zero-knowledge encryption design, the tokens stored in aliasvault.xml are API session tokens that cannot decrypt the vault on their own: the master password is required for that. So while this isn't a direct vault compromise risk, there's no reason to include them in backups either."
INFO
Published Date :
Feb. 23, 2026, 6:16 a.m.
Last Modified :
March 12, 2026, 4:19 p.m.
Remotely Exploit :
No
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 2.0 | LOW | [email protected] | ||||
| CVSS 3.1 | LOW | [email protected] | ||||
| CVSS 4.0 | LOW | [email protected] |
Solution
- Upgrade AliasVault App to version 0.26.0.
- Ensure the affected component is updated.
- Remove sensitive tokens from backups.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-2974.
| URL | Resource |
|---|---|
| https://github.com/aliasvault/aliasvault/commit/873ecc03f92238e162f98a068ad56069a922b4f6 | Patch |
| https://github.com/aliasvault/aliasvault/issues/1497 | Issue Tracking |
| https://github.com/aliasvault/aliasvault/issues/1497#issue-3855176470 | Issue Tracking |
| https://github.com/aliasvault/aliasvault/pull/1499 | Issue Tracking |
| https://github.com/aliasvault/aliasvault/releases/tag/0.26.0 | Release Notes |
| https://vuldb.com/?ctiid.347340 | Permissions Required VDB Entry |
| https://vuldb.com/?id.347340 | Third Party Advisory VDB Entry |
| https://vuldb.com/?submit.756058 | Third Party Advisory VDB Entry |
| https://vuldb.com/?submit.756059 | Third Party Advisory VDB Entry |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-2974 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-2974
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-2974 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-2974 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Mar. 12, 2026
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:a:aliasvault:aliasvault:*:*:*:*:*:*:*:* versions up to (including) 0.25.3 Added Reference Type VulDB: https://github.com/aliasvault/aliasvault/commit/873ecc03f92238e162f98a068ad56069a922b4f6 Types: Patch Added Reference Type VulDB: https://github.com/aliasvault/aliasvault/issues/1497 Types: Issue Tracking Added Reference Type VulDB: https://github.com/aliasvault/aliasvault/issues/1497#issue-3855176470 Types: Issue Tracking Added Reference Type VulDB: https://github.com/aliasvault/aliasvault/pull/1499 Types: Issue Tracking Added Reference Type VulDB: https://github.com/aliasvault/aliasvault/releases/tag/0.26.0 Types: Release Notes Added Reference Type VulDB: https://vuldb.com/?ctiid.347340 Types: Permissions Required, VDB Entry Added Reference Type VulDB: https://vuldb.com/?id.347340 Types: Third Party Advisory, VDB Entry Added Reference Type VulDB: https://vuldb.com/?submit.756058 Types: Third Party Advisory, VDB Entry Added Reference Type VulDB: https://vuldb.com/?submit.756059 Types: Third Party Advisory, VDB Entry -
New CVE Received by [email protected]
Feb. 23, 2026
Action Type Old Value New Value Added Description A vulnerability was identified in AliasVault App up to 0.25.3 on Android/iOS. This vulnerability affects unknown code of the file shared_prefs/aliasvault.xml of the component Backup Handler. The manipulation of the argument accessToken/refreshToken/metadata/key_derivation_params/auth_methods leads to exposure of backup file to an unauthorized control sphere. An attack has to be approached locally. The attack is considered to have high complexity. It is stated that the exploitability is difficult. The exploit is publicly available and might be used. Upgrading to version 0.26.0 is able to resolve this issue. The identifier of the patch is 873ecc03f92238e162f98a068ad56069a922b4f6/0bd662320174d8265dfe3b05a04bc13efc960532. It is recommended to upgrade the affected component. The creator of the software explains: "Because of AliasVault's zero-knowledge encryption design, the tokens stored in aliasvault.xml are API session tokens that cannot decrypt the vault on their own: the master password is required for that. So while this isn't a direct vault compromise risk, there's no reason to include them in backups either." Added CVSS V4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Added CVSS V3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N Added CVSS V2 (AV:L/AC:H/Au:S/C:P/I:N/A:N) Added CWE CWE-285 Added CWE CWE-530 Added Reference https://github.com/aliasvault/aliasvault/commit/873ecc03f92238e162f98a068ad56069a922b4f6 Added Reference https://github.com/aliasvault/aliasvault/issues/1497 Added Reference https://github.com/aliasvault/aliasvault/issues/1497#issue-3855176470 Added Reference https://github.com/aliasvault/aliasvault/pull/1499 Added Reference https://github.com/aliasvault/aliasvault/releases/tag/0.26.0 Added Reference https://vuldb.com/?ctiid.347340 Added Reference https://vuldb.com/?id.347340 Added Reference https://vuldb.com/?submit.756058 Added Reference https://vuldb.com/?submit.756059